Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix warning on conversion of anon func with implicit parameters #59522

Merged
merged 3 commits into from
Feb 15, 2022

Conversation

jcouv
Copy link
Member

@jcouv jcouv commented Feb 13, 2022

Fixes #59336

@jcouv jcouv marked this pull request as ready for review February 14, 2022 04:50
@jcouv jcouv requested a review from a team as a code owner February 14, 2022 04:50
@@ -1357,7 +1356,6 @@ internal sealed class PlainUnboundLambdaState : UnboundLambdaState
_isStatic = isStatic;
}

public override bool HasNames { get { return !_parameterNames.IsDefault; } }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so this member was just totally redundant in practice?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, they have the same meaning. We had HasNames, HasSignature and I was adding yet another one...

@jcouv jcouv changed the title Fix nullable warning on conversion of anonymous function with implicit parameters Fix warning on conversion of anon func with implicit parameters Feb 15, 2022
@jcouv jcouv merged commit f767c70 into dotnet:main Feb 15, 2022
@jcouv jcouv deleted the implicit-parameters branch February 15, 2022 19:16
@ghost ghost added this to the Next milestone Feb 15, 2022
@RikkiGibson RikkiGibson modified the milestones: Next, 17.2.P2 Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants